bpo-36688: Adding an implementation of RLock in _dummy_thread#12943
bpo-36688: Adding an implementation of RLock in _dummy_thread#12943vstinner merged 3 commits intopython:masterfrom
Conversation
|
Hello, and thanks for your contribution! I'm a bot set up to make sure that the project can legally accept your contribution by verifying you have signed the PSF contributor agreement (CLA). Unfortunately we couldn't find an account corresponding to your GitHub username on bugs.python.org (b.p.o) to verify you have signed the CLA (this might be simply due to a missing "GitHub Name" entry in your b.p.o account settings). This is necessary for legal reasons before we can look at your contribution. Please follow the steps outlined in the CPython devguide to rectify this issue. You can check yourself to see if the CLA has been received. Thanks again for your contribution, we look forward to reviewing it! |
skoslowski
left a comment
There was a problem hiding this comment.
Thanks for your contribution. I ran your tests and double-checked with the documentation
|
GH-14144 is a backport of this pull request to the 3.7 branch. |
|
GH-14145 is a backport of this pull request to the 3.8 branch. |
Implementing an extremely simple RLock that extends Lock. It accepts multiple acquire() calls and just as many release() calls but no more. This should be sufficient for the _dummy_thread module and fixes issue 36688 where python -c 'import dummy_threading' would cause an ImportError.
I also added tests for RLock in Lib/test/test_dummy_thread and made it executable.
https://bugs.python.org/issue36688